Skip to main content
Brighton and Hove City Council

Brownfield land

There is a problem

  • GeoX,GeoY column must have valid coordinates

SHLAA0858

SiteReference
SHLAA0858
SiteNameAddress
27-31 Church Street Brighton
Deliverable
yes
HazardousSubstances
yes
Hectares
0.12
MinNetDwellings
NetDwellingsRangeFrom
9
NetDwellingsRangeTo
10
OwnershipStatus
not-owned-by-a-public-authority
PermissionDate
2013-02-08
PermissionType
full-planning-permission
PlanningHistory
https://planningapps.brighton-hove.gov.uk/online-applications/applicationDetails.do?activeTab=summary&keyVal=QHJ2QTDMMNR00|https://planningapps.brighton-hove.gov.uk/online-applications/applicationDetails.do?activeTab=summary&keyVal=ZZZR5ZDMXE648|https://planningapps.brighton-hove.gov.uk/online-applications/applicationDetails.do?activeTab=summary&keyVal=ZZZR6FDMXE938|https://planningapps.brighton-hove.gov.uk/online-applications/applicationDetails.do?activeTab=summary&keyVal=ZZZR6JDMXE885|https://planningapps.brighton-hove.gov.uk/online-applications/applicationDetails.do?activeTab=summary&keyVal=ZZZR7GDMXE012|https://planningapps.brighton-hove.gov.uk/online-applications/applicationDetails.do?activeTab=summary&keyVal=ZZZR7KDMXE624
PlanningStatus
permissioned
SiteplanURL
https://new.brighton-hove.gov.uk/sites/default/files/planning_bc_regen/policy/brownfield-sites/shlaa0858-27-31-church-street-brighton.pdf
GeoX
POINT(-0.141895 50.8246)
GeoY
POINT(-0.141895 50.8246)
Notes
BH2011/02401 Commenced although currently being used as secure gated car park. Draft City Plan Part 2 Allocation. Application BH2020/02801 for Office Under Consideration 2020
OrganisationLabel
OrganisationURI
LastUpdatedDate
2022-12-05
FirstAddedDate
2017-09-19
EndDate
GeoX,GeoY

Geometry must use WGS84, OSGB or Mercator coordinates

Geometry must use WGS84, OSGB or Mercator coordinates

Geometry must use WGS84, OSGB or Mercator coordinates

How to improve Brighton and Hove City Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL